Computerized system and method for generating and dynamically updating a dashboard of multiple processes and operations across platforms

ABSTRACT

Disclosed are systems and methods for improving interactions with and between computers in content providing, searching and/or hosting systems supported by or configured with devices, servers and/or platforms. The disclosed systems and methods provide a novel framework that automatically generates and dynamically updates a multi-displayed dashboard of consistent instances on separate devices and/or network locations. The disclosed framework produces and displays an interactive dashboard including electronic tiles representing data of multiple processes and operations. The framework includes functionality for uniformly maintaining the display characteristics, such as the look and feel of the dashboard and the tiles included therein, across platforms of different devices, operating environments and/or display capabilities.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority from U.S. ProvisionalApplication No. 62/933,759, filed Nov. 11, 2019, entitled “Dashboard OfMultiple Process And Operations Information Tiles In A Mobile App ServerAnd System,” which is incorporated herein by reference in its entirety.

This application includes material that is subject to copyrightprotection. The copyright owner has no objection to the facsimilereproduction by anyone of the patent disclosure, as it appears in thePatent and Trademark Office files or records, but otherwise reserves allcopyright rights whatsoever.

FIELD

Some embodiments relate generally to improving the performance ofnetwork-based computerized content hosting and providing devices,systems and/or platforms by modifying the capabilities and providingnon-native functionality to such devices, systems and/or platformsthrough a novel and improved asset management and visualizationframework for automatically generating and dynamically updating adashboard that provides data related to multiple processes andoperations across platforms of different devices, operating environmentsand/or display capabilities, or some combination thereof.

BACKGROUND

As more data get logged into databases, cloud servers, operationalhistorians and/or any other type of software-based and hardwaresupported local and/or network configured data store(s), customers, andthe systems and services associated therewith, are looking forcomputerized mechanisms for managing, understanding and displaying thedata.

Conventional mechanisms are failing, as they are leading to loss ofdata, increased bottlenecking and inefficiency in data reception andpresentation, and an overall lack of organization in the way the data isprotected, provided and displayed to users.

Moreover, different types of content such as text, audio, video orcombinations thereof are provided to the users via, for example, theirpersonal computing devices, smart phones, tablets, smart phones, and thelike. These different types of devices host or implement different typesof platforms via different hardware configurations that provide entirelydifferent operating environments and/or display capabilities. This inturn has resulted in the development of various proprietary andplatform-agnostic content formats.

SUMMARY

Thus, the existing technological failings in the computerized fields ofdata storage, retention and presentation are currently lacking online orcomputerized mechanisms that enable automatic, dynamically determinedand updated interactions to facilitate how and which manner the data iscompiled, presented and/or interacted with. Some embodiments of thedisclosed systems and methods, among other features, provide thedisclosed asset management and visualization framework to address theseneeds and more.

According to some embodiments, the disclosed framework executes systemsand methods that automatically generate and dynamically update aninteractive dashboard interface that comprises digital informationrelated to multiple processes and operations. In some embodiments, thedashboard enables a uniform look and feel across platforms, devicesand/or services being utilized to view and/or interact with thedashboard and/or interface objects (e.g., tiles) included therein.

In some embodiments, users compose a dashboard which is a collection ofinformation tiles. The tiles, for example, can detail process datatrends, status charts, and the like. The tiles provide an overview ofassets' operations at a location, within an infrastructure of a web pageor other desired environment.

In some embodiments, this collection of tiles is typically related to asingle logical entity such as an asset or a facility and is organized,in some embodiments, to progressively disclose more information fromleft to right and top to bottom within the dashboard. In someembodiments, once the dashboard is configured, when a user logs into thenetwork resource, they are able to view the previously configured (e.g.,authored or customized) dashboard in a mobile friendly format andlayout. The enables users to author their dashboards once but view themin a web-enabled device and/or a mobile device as desired.

This functionality makes all the information available in the dashboardavailable for users on the go, without needing to author a dashboard formobile use. Further, in some embodiments, any changes done to thedashboard in the web or other environment are automatically reflected inthe mobile. The dashboard in mobiles also allows for drill through intoeach of the information tiles for more details and interactions.

According to some embodiments, reference to a network resource caninclude, but is not limited to, a mobile application (“App”, usedinterchangeably), a web hosted page accessible via a browser, an itemstored within a cloud environment, or a locally stored item that isaccessible directly from a user's device or via a network or other type(e.g., near field connection (NFC) connection), and the like.

In some embodiments, the dashboard can comprise a user (e.g., an author)processing only a predetermined number of times (e.g., once, forexample)—that is, configuring the dashboard once, for example, andhaving this configuration dictate how other instances of the dashboardare depicted. Some embodiments provide access anywhere in a mobile App.In some embodiments, multiple process information tiles can provide aquick overview of an entire manufacturing process, operational facilityor other operation or facility of interest.

In some embodiments, the layout of information tiles in the dashboard inthe mobile App can be automatically adapted to the screen size,resolution and orientation, among other features as discussed below. Insome embodiments, changes to the configuration of the dashboard in theweb environment can be automatically reflected in the mobile device. Insome embodiments, the deployment and/or presentation of the latestversion of a dashboard can be accelerated, provided to or automaticallymatriculated to all users, serving as a very easy to use collaborationand communication mechanism. Such deployment can be based onadministrator input, or server or device input, based on altered ornewly detected capability information or tile information.

For example, an administrator can change the configuration tile ofstatus chart every morning to reflect the most overheating pump or otherasset with behavior or characteristics of interest from the previousday, so all users automatically view it for their analyses. Someembodiments enable the administrator to disseminate information to usersin administrator-selected groups.

Some embodiments include tiles in the dashboard. In some embodiments,the dashboard can be found in a mobile App. In some embodiments, thetiles in dashboards can be automatically updated on a periodic orsubstantially continuous basis. In some embodiments, the combination ofthese features can create an author once functionality. In someembodiments, author once can have access in multiple formats. Someembodiments include easy to use multiple formats, collaborative,automatic updates in dashboards in a mobile device for mobile users.Some embodiments include quick, useful and actionable overview of theirentire operation or facility of interest.

In some embodiments, a list of dashboards can be authored in a desktopand/or mobile (or tablet, used interchangeably)-based web environment.In some embodiments, the dashboards can be readily visible on a mobiledevice for users without the need to expend any extra effort. In someembodiments, the dashboards can be automatically adopted to the mobilescreen format. Some embodiments comprise efficient engineering that canenable author-once-access anywhere plant process information dashboardfor users.

Thus, as discussed herein, according to some embodiments, the disclosedsystems and methods provide a platform-independent application frameworkthat enables a platform-neutral dashboard environment that maintains asimilar look and feel of the data across platforms, interfaces andapplications. Therefore, for example, how a dashboard is displayed, andthe mechanisms in which the data included therein is displayed on thedashboard can be maintained on whether the dashboard is being loaded anddisplayed within a browser or on a mobile application (“App”).

According to some embodiments, a computer-implemented method isdisclosed which automatically generates and dynamically updates andmaintains a multi-displayed dashboard of consistent instances acrossseparate devices and/or network locations. According to someembodiments, the method produces and displays an interactive dashboardincluding electronic tiles representing data of multiple processes andoperations, whereby the dashboard's look and feel are maintainedregardless of the computing/display environment displaying thedashboard.

Some embodiments provide a non-transitory computer-readable storagemedium for carrying out the above mentioned technical steps of theframework's functionality. The non-transitory computer-readable storagemedium has tangibly stored thereon, or tangibly encoded thereon,computer readable instructions that when executed by a device (e.g.,application server, messaging server, email server, ad server, contentserver and/or client device, and the like) cause at least one processorto perform a method for a novel and improved framework for automaticallygenerating and dynamically updating a dashboard that provides datarelated to multiple processes and operations across platforms ofdifferent devices, operating environments and/or display capabilities,or some combination thereof.

In accordance with one or more embodiments, a system is provided thatcomprises one or more computing devices configured to providefunctionality in accordance with such embodiments. In accordance withone or more embodiments, functionality is embodied in steps of a methodperformed by at least one computing device. In accordance with one ormore embodiments, program code (or program logic) executed by aprocessor(s) of a computing device to implement functionality inaccordance with one or more such embodiments is embodied in, by and/oron a non-transitory computer-readable medium.

According to some embodiments, a computing device is disclosed whichcomprises: one or more processors; and a non-transitorycomputer-readable memory having stored therein computer-executableinstructions, that when executed by the one or more processors, causethe one or more processors to perform actions comprising: receiving,over a network, electronic data corresponding to an operation of a setof physical assets at a location, the electronic data compiled as tiles,such that each tile corresponds to operation of an asset within the setof physical assets; receiving information setting a configuration of adashboard for a first device, the received dashboard informationcomprising information indicating how the tiles are to be displayed on auser interface (UI) of the first device; storing, in a databaseassociated with the computing device, the dashboard information;receiving, over a network, from a second device, a request to access anddisplay the dashboard; analyzing, based on the request, capabilityinformation of the second device, and based on the analysis, determiningdisplay and rendering capabilities of the second device; modifying, inresponse to the second device request, the stored dashboard informationbased on the determined display and rendering capabilities of the seconddevice; compiling a version of the dashboard for display on a display ofthe second device based on the modified dashboard information; andautomatically causing, over the network, the compiled dashboard to bedisplayed on the display of the second device.

In some embodiments, the compiling a version further comprises: creatinga new version of the dashboard based on the determined display andrendering capabilities of the second device; and storing the new versionin association with the dashboard information. In some embodiments, thecommunication is based on the new version.

In some embodiments, the compiling a version further comprises:modifying attributes of the dashboard information based on thedetermined display and rendering capabilities of the second device; andstoring the modified attributes in the storage in relation to the storeddashboard information. In some embodiments, the communication is basedon the dashboard information and stored modified attributes.

In some embodiments, the stored dashboard information further comprisesthe electronic data of the set of tiles.

In some embodiments, the database is a cloud-based storage.

In some embodiments, the request to access and display the dashboardcomprises the capability information.

In some embodiments, the dashboard information comprises data selectedfrom a group consisting of: display size, color, dimension, font,layout, format, configuration, layer, organization, pixel data,resolution, scrollability, amount of available screen real estate,operating system, network bandwidth, service provider and user identity.

In some embodiments, the dashboard information is stored as a templateindicating a configuration, format and layout of the set of tiles.

In some embodiments, the capability information of the second devicecomprises data selected from a group consisting of: display size, color,dimension, font, layout, format, configuration, layer, organization,pixel data, resolution, scrollability, amount of available screen realestate, operating system, network bandwidth, service provider and useridentity.

In some embodiments, the actions further comprise: receiving informationrelated to an update of electronic data related to a first tile withinthe set of tiles; and updating, within a dashboard displayed on thefirst device, content displayed within the first tile based on thereceived information.

In some embodiments, the actions further comprise: retrieving, from thedatabase, dashboard information for the second device; modifying theupdated first tile based on the second device dashboard information; andcommunicating information related to the modified tile to the dashboardfor display on the second device.

In some embodiments, the actions further comprise: causing, over anetwork, a dashboard display on the first device and the dashboarddisplay on the second device to operate as a collaborate environment,such that modifications on one device are automatically caused to beperformed on the other device.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features, and advantages of thedisclosure will be apparent from the following description ofembodiments as illustrated in the accompanying drawings, in whichreference characters refer to the same parts throughout the variousviews. The drawings are not necessarily to scale, emphasis instead beingplaced upon illustrating principles of the disclosure:

FIG. 1 is a schematic diagram illustrating an example of a networkwithin which the systems and methods disclosed herein could beimplemented according to some embodiments of the present disclosure;

FIG. 2 is a schematic diagram illustrating an example of a networkwithin which the systems and methods disclosed herein could beimplemented according to some embodiments of the present disclosure;

FIG. 3 depicts is a schematic diagram illustrating an example of clientdevice according to some embodiments of the present disclosure;

FIG. 4 is a block diagram illustrating components of an exemplary systemin accordance with embodiments of the present disclosure;

FIG. 5 illustrates a non-limiting example of a list of dashboards in weband mobile view according to some embodiments of the present disclosure;

FIG. 6 illustrates a non-limiting example embodiment of an opendashboard in a web environment with adoptive display in a mobileenvironment according to some embodiments of the present disclosure;

FIG. 7 illustrates a non-limiting example embodiment of a dashboardaccording to some embodiments of the present disclosure; and

FIG. 8 details a non-limiting data flow according to some embodiments ofthe present disclosure.

DESCRIPTION OF EMBODIMENTS

The present disclosure will now be described more fully hereinafter withreference to the accompanying drawings, which form a part hereof, andwhich show, by way of non-limiting illustration, certain exampleembodiments. Subject matter may, however, be embodied in a variety ofdifferent forms and, therefore, covered or claimed subject matter isintended to be construed as not being limited to any example embodimentsset forth herein; example embodiments are provided merely to beillustrative. Likewise, a reasonably broad scope for claimed or coveredsubject matter is intended. Among other things, for example, subjectmatter may be embodied as methods, devices, components, or systems.Accordingly, embodiments may, for example, take the form of hardware,software, firmware or any combination thereof (other than software perse). The following detailed description is, therefore, not intended tobe taken in a limiting sense.

Throughout the specification and claims, terms may have nuanced meaningssuggested or implied in context beyond an explicitly stated meaning.Likewise, the phrase “in some embodiments” as used herein does notnecessarily refer to the same embodiment and the phrase “in anotherembodiment” as used herein does not necessarily refer to a differentembodiment. It is intended, for example, that claimed subject matterinclude combinations of example embodiments in whole or in part.

In general, terminology may be understood at least in part from usage incontext. For example, terms, such as “and”, “or”, or “and/or,” as usedherein may include a variety of meanings that may depend at least inpart upon the context in which such terms are used. Typically, “or” ifused to associate a list, such as A, B or C, is intended to mean A, B,and C, here used in the inclusive sense, as well as A, B or C, here usedin the exclusive sense. In addition, the term “one or more” as usedherein, depending at least in part upon context, may be used to describeany feature, structure, or characteristic in a singular sense or may beused to describe combinations of features, structures or characteristicsin a plural sense. Similarly, terms, such as “a,” “an,” or “the,” again,may be understood to convey a singular usage or to convey a pluralusage, depending at least in part upon context. In addition, the term“based on” may be understood as not necessarily intended to convey anexclusive set of factors and may, instead, allow for existence ofadditional factors not necessarily expressly described, again, dependingat least in part on context.

The present disclosure is described below with reference to blockdiagrams and operational illustrations of methods and devices. It isunderstood that each block of the block diagrams or operationalillustrations, and combinations of blocks in the block diagrams oroperational illustrations, can be implemented by means of analog ordigital hardware and computer program instructions. These computerprogram instructions can be provided to a processor of a general purposecomputer to alter its function as detailed herein, a special purposecomputer, ASIC, or other programmable data processing apparatus, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, implement thefunctions/acts specified in the block diagrams or operational block orblocks. In some alternate implementations, the functions/acts noted inthe blocks can occur out of the order noted in the operationalillustrations. For example, two blocks shown in succession can in factbe executed substantially concurrently or the blocks can sometimes beexecuted in the reverse order, depending upon the functionality/actsinvolved.

For the purposes of this disclosure, a non-transitory computer readablemedium (or computer-readable storage medium/media) stores computer data,which data can include computer program code (or computer-executableinstructions) that is executable by a computer, in machine readableform. By way of example, and not limitation, a computer readable mediummay comprise computer readable storage media, for tangible or fixedstorage of data, or communication media for transient interpretation ofcode-containing signals. Computer readable storage media, as usedherein, refers to physical or tangible storage (as opposed to signals)and includes without limitation volatile and non-volatile, removable andnon-removable media implemented in any method or technology for thetangible storage of information such as computer-readable instructions,data structures, program modules or other data. Computer readablestorage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM,flash memory or other solid state memory technology, CD-ROM, DVD, orother optical storage, cloud storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any otherphysical or material medium which can be used to tangibly store thedesired information or data or instructions and which can be accessed bya computer or processor.

For the purposes of this disclosure the term “server” should beunderstood to refer to a service point which provides processing,database, and communication facilities. By way of example, and notlimitation, the term “server” can refer to a single, physical processorwith associated communications and data storage and database facilities,or it can refer to a networked or clustered complex of processors andassociated network and storage devices, as well as operating softwareand one or more database systems and application software that supportthe services provided by the server. Cloud servers are examples.

For the purposes of this disclosure, a “network” should be understood torefer to a network that may couple devices so that communications may beexchanged, such as between a server and a client device or other typesof devices, including between wireless devices coupled via a wirelessnetwork, for example. A network may also include mass storage, such asnetwork attached storage (NAS), a storage area network (SAN), a contentdelivery network (CDN) or other forms of computer or machine readablemedia, for example. A network may include the Internet, one or morelocal area networks (LANs), one or more wide area networks (WANs),wire-line type connections, wireless type connections, cellular or anycombination thereof. Likewise, sub-networks, which may employ differingarchitectures or may be compliant or compatible with differingprotocols, may interoperate within a larger network.

For purposes of this disclosure, a “wireless network” should beunderstood to couple client devices with a network. A wireless networkmay employ stand-alone ad-hoc networks, mesh networks, Wireless LAN(WLAN) networks, cellular networks, or the like. A wireless network mayfurther employ a plurality of network access technologies, includingWi-Fi, Long Term Evolution (LTE), WLAN, Wireless Router (WR) mesh, or2nd, 3rd, 4^(th) or 5^(th) generation (2G, 3G, 4G or 5G) cellulartechnology, Bluetooth, 802.11b/g/n, or the like. Network accesstechnologies may enable wide area coverage for devices, such as clientdevices with varying degrees of mobility, for example.

In short, a wireless network may include virtually any type of wirelesscommunication mechanism by which signals may be communicated betweendevices, such as a client device or a computing device, between orwithin a network, or the like.

A computing device may be capable of sending or receiving signals, suchas via a wired or wireless network, or may be capable of processing orstoring signals, such as in memory as physical memory states, and may,therefore, operate as a server. Thus, devices capable of operating as aserver may include, as examples, dedicated rack-mounted servers, desktopcomputers, laptop computers, set top boxes, integrated devices combiningvarious features, such as two or more features of the foregoing devices,or the like.

For purposes of this disclosure, a client (or consumer or user) devicemay include a computing device capable of sending or receiving signals,such as via a wired or a wireless network. A client device may, forexample, include a desktop computer or a portable device, such as acellular telephone, a smart phone, a display pager, a radio frequency(RF) device, an infrared (IR) device an Near Field Communication (NFC)device, a Personal Digital Assistant (PDA), a handheld computer, atablet computer, a phablet, a laptop computer, a set top box, a wearablecomputer, smart watch, an integrated or distributed device combiningvarious features, such as features of the forgoing devices, or the like.

A client device may vary in terms of capabilities or features. Claimedsubject matter is intended to cover a wide range of potentialvariations, such as a web-enabled client device or previously mentioneddevices may include a high-resolution screen (HD or 4K for example), oneor more physical or virtual keyboards, mass storage, one or moreaccelerometers, one or more gyroscopes, global positioning system (GPS)or other location-identifying type capability, or a display with a highdegree of functionality, such as a touch-sensitive color 2D or 3Ddisplay, for example.

Certain embodiments will now be described in greater detail withreference to the figures. In general, with reference to FIG. 1 , asystem 100 in accordance with some embodiments of the present disclosureis shown. FIG. 1 shows components of a general environment in which thesystems and methods discussed herein may be practiced. Not all thecomponents may be required to practice the disclosure, and variations inthe arrangement and type of the components may be made without departingfrom the spirit or scope of the disclosure. As shown, system 100 of FIG.1 includes local area networks (“LANs”)/wide area networks(“WANs”)—network 105, wireless network 110, mobile devices (clientdevices) 102-104 and client device 101. FIG. 1 additionally includes avariety of servers, such as content server 106 and application (or“App”) server 108.

Some embodiments of mobile devices 102-104 may include virtually anyportable computing device capable of receiving and sending a messageover a network, such as network 105, wireless network 110, or the like.Mobile devices 102-104 may also be described generally as client devicesthat are configured to be portable. Thus, mobile devices 102-104 mayinclude virtually any portable computing device capable of connecting toanother computing device and receiving information, as discussed above.

Mobile devices 102-104 also may include at least one client applicationthat is configured to receive content from another computing device. Insome embodiments, mobile devices 102-104 may also communicate withnon-mobile client devices, such as client device 101, or the like. Insome embodiments, such communications may include sending and/orreceiving messages, creating and uploading documents, searching for,viewing and/or sharing memes, photographs, digital images, audio clips,video clips, or any of a variety of other forms of communications.

Client devices 101-104 may be capable of sending or receiving signals,such as via a wired or wireless network, or may be capable of processingor storing signals, such as in memory as physical memory states, andmay, therefore, operate as a server.

In some embodiments, wireless network 110 is configured to couple mobiledevices 102-104 and its components with network 105. Wireless network110 may include any of a variety of wireless sub-networks that mayfurther overlay stand-alone ad-hoc networks, and the like, to provide aninfrastructure-oriented connection for mobile devices 102-104.

In some embodiments, network 105 is configured to couple content server106, application server 108, or the like, with other computing devices,including, client device 101, and through wireless network 110 to mobiledevices 102-104. Network 105 is enabled to employ any form of computerreadable media or network for communicating information from oneelectronic device to another.

In some embodiments, the content server 106 may include a device thatincludes a configuration to provide any type or form of content via anetwork to another device. Devices that may operate as content server106 include personal computers, desktop computers, multiprocessorsystems, microprocessor-based or programmable consumer electronics,network PCs, servers, and the like. In some embodiments, content server106 can further provide a variety of services that include, but are notlimited to, email services, instant messaging (IM) services, streamingand/or downloading media services, search services, photo services, webservices, social networking services, news services, third-partyservices, audio services, video services, SMS services, MMS services,FTP services, voice over IP (VOIP) services, or the like. Such services,for example the email services and email platform, can be provided viathe message server 120.

In some embodiments, users are able to access services provided byservers 106 and 108. This may include in a non-limiting example,authentication servers, search servers, email servers, social networkingservices servers, SMS servers, IM servers, MMS servers, exchangeservers, photo-sharing services servers, and travel services servers,via the network 105 using their various devices 101-104.

In some embodiments, application server 108, for example, can storevarious types of applications and application related informationincluding application data and user profile information (e.g.,identifying, generated and/or observed information associated with auser).

In some embodiments, content server 106 and app server 108 can storevarious types of data related to the content and services each provide,observe, identify, determine, generate, modify, retrieve and/or collect.Such data can be stored in an associated content database 107, asdiscussed in more detail below.

In some embodiments, server 106 and/or 108 can be embodied as a cloudserver or configured for hosting cloud services, as discussed herein.

In some embodiments, the network 105 is also coupled with/connected to aTrusted Search Server (TSS) which can be utilized to render content inaccordance with the embodiments discussed herein. Embodiments existwhere the TSS functionality can be embodied within servers 106 and 108.

Moreover, although FIG. 1 illustrates servers 106 and 108 as singlecomputing devices, respectively, the disclosure is not so limited. Forexample, one or more functions of servers 106 and 108 may be distributedacross one or more distinct computing devices. Moreover, in someembodiments, servers 106 and 108 may be integrated into a singlecomputing device, without departing from the scope of the presentdisclosure.

Additionally, while the illustrated embodiment in FIG. 1 depicts onlyservers 106 and 108, it should not be construed as limiting, as any typeand number of servers can be included therein.

Turning to FIG. 2 , computer system 210 is depicted and is anon-limiting example embodiment of system 100 discussed above inrelation to FIG. 1 .

FIG. 2 illustrates a computer system 210 enabling or operating anembodiment of system 100 of FIG. 1 , as discussed below. In someembodiments, computer system 210 can include and/or operate and/orprocess computer-executable code of one or more of the above-mentionedprogram logic, software modules, and/or systems. Further, in someembodiments, the computer system 210 can operate and/or displayinformation within one or more graphical user interfaces. In someembodiments, the computer system 210 can comprise a cloud server and/orcan be coupled to one or more cloud-based server systems.

In some embodiments, the system 210 can comprise at least one computingdevice 230 including at least one processor 232. In some embodiments,the at least one processor 232 can include a processor residing in, orcoupled to, one or more server platforms. In some embodiments, thesystem 210 can include a network interface 235 a and an applicationinterface 235 b coupled to the least one processor 232 capable ofprocessing at least one operating system 234. Further, in someembodiments, the interfaces 235 a, 235 b coupled to at least oneprocessor 232 can be configured to process one or more of the softwaremodules 238 (e.g., such as enterprise applications). In someembodiments, the software modules 238 can include server-based software,and can operate to host at least one user account and/or at least oneclient account, and operating to transfer data between one or more ofthese accounts using the at least one processor 232.

With the above embodiments in mind, it should be understood that someembodiments can employ various computer-implemented operations involvingdata stored in computer systems. Moreover, the above-described databasesand models described throughout can store analytical models and otherdata on computer-readable storage media within the system 210 and oncomputer-readable storage media coupled to the system 210. In addition,the above-described applications of the system can be stored onnon-transitory computer-readable storage media within the system 210 andon computer-readable storage media coupled to the system 210.

In some embodiments, the system 210 can comprise at least onenon-transitory computer readable medium 236 coupled to at least one datasource 237 a, and/or at least one data storage device 237 b, and/or atleast one input/output device 237 c. In some embodiments, the disclosedsystems and methods can be embodied as computer readable code on acomputer readable medium 236. In some embodiments, the computer readablemedium 236 can be any data storage device that can store data, which canthereafter be read by a computer system (such as the system 210). Insome embodiments, the computer readable medium 236 can be any physicalor material medium that can be used to tangibly store the desiredinformation or data or instructions and which can be accessed by acomputer or processor 232. In some embodiments, at least one of thesoftware modules 238 can be configured within the system to output datato at least one user 231 via at least one graphical user interfacerendered on at least one digital display.

In some embodiments, the non-transitory computer readable medium 236 canbe distributed over a conventional computer network via the networkinterface 235 a where the system embodied by the computer readable codecan be stored and executed in a distributed fashion. For example, insome embodiments, one or more components of the system 210 can becoupled to send and/or receive data through a local area network (“LAN”)239 a and/or an internet coupled network 239 b (e.g., such as a wirelessinternet). In some further embodiments, the networks 239 a, 239 b caninclude wide area networks (“WAN”), direct connections (e.g., through auniversal serial bus port), or other forms of computer-readable media236, or any combination thereof.

In some embodiments, components of the networks 239 a, 239 b can includeany number of user devices such as personal computers including forexample desktop computers, and/or laptop computers, or any fixed,generally non-mobile internet appliances coupled through the LAN 239 a.For example, some embodiments include personal computers 240 a coupledthrough the LAN 239 a that can be configured for any type of userincluding an administrator. Other embodiments can include personalcomputers coupled through network 239 b. In some further embodiments,one or more components of the system 210 can be coupled to send orreceive data through an internet network (e.g., such as network 239 b).For example, some embodiments include at least one user 231 coupledwirelessly and accessing one or more software modules of the systemincluding at least one enterprise application 238 via an input andoutput (“I/O”) device 237 c. In some other embodiments, the system 210can enable at least one user 231 to be coupled to access enterpriseapplications 238 via an I/O device 237 c through LAN 239 a. In someembodiments, the user 231 can comprise a user 231 a coupled to thesystem 210 using a desktop computer, and/or laptop computers, or anyfixed, generally non-mobile internet appliances coupled through theinternet 239 b. In some embodiments, the user 231 can comprise a mobileuser 231 b coupled to the system 210. In some embodiments, the user 231b can use any mobile computing device 231 c to wirelessly coupled to thesystem 210, including, but not limited to, personal digital assistants,and/or cellular phones, mobile phones, or smart phones, and/or pagers,and/or digital tablets, and/or fixed or mobile internet appliances.

FIG. 3 is a schematic diagram illustrating a client device showing anexample embodiment of a client device that may be used within thepresent disclosure. Client device 300 may include many more or lesscomponents than those shown in FIG. 3 . However, the components shownare sufficient to disclose an illustrative embodiment for implementingthe present disclosure. Client device 300 may represent, for example,client devices discussed above in relation to FIGS. 1-2 .

As shown in FIG. 3 , in some embodiments, Client device 300 includes aprocessing unit (CPU) 322 in communication with a mass memory 330 via abus 324. In some embodiments, Client device 300 also includes a powersupply 326, one or more network interfaces 350, an audio interface 352,a display 354, a keypad 356, an illuminator 358, an input/outputinterface 360, a haptic interface 362, an optional global positioningsystems (GPS) receiver 364 and a camera(s) or other optical, thermal orelectromagnetic sensors 366. Device 300 can include one camera/sensor366, or a plurality of cameras/sensors 366, as understood by those ofskill in the art. Power supply 326 provides power to Client device 300.

Client device 300 may optionally communicate with a base station (notshown), or directly with another computing device. Network interface 350is sometimes known as a transceiver, transceiving device, or networkinterface card (NIC).

In some embodiments, audio interface 352 is arranged to produce andreceive audio signals such as the sound of a human voice. Display 354may be a liquid crystal display (LCD), gas plasma, light emitting diode(LED), or any other type of display used with a computing device.Display 354 may also include a touch sensitive screen arranged toreceive input from an object such as a stylus or a digit from a humanhand.

Keypad 356 may comprise any input device arranged to receive input froma user. Illuminator 358 may provide a status indication and/or providelight.

In some embodiments, client device 300 also comprises input/outputinterface 360 for communicating with external. Input/output interface360 can utilize one or more communication technologies, such as USB,infrared, Bluetooth™, or the like. In some embodiments, haptic interface362 is arranged to provide tactile feedback to a user of the clientdevice.

Optional GPS transceiver 364 can determine the physical coordinates ofClient device 300 on the surface of the Earth, which typically outputs alocation as latitude and longitude values. GPS transceiver 364 can alsoemploy other geo-positioning mechanisms, including, but not limited to,triangulation, assisted GPS (AGPS), E-OTD, CI, SAI, ETA, BSS or thelike, to further determine the physical location of Client device 300 onthe surface of the Earth. In some embodiments, however, Client devicemay through other components, provide other information that may beemployed to determine a physical location of the device, including forexample, a MAC address, Internet Protocol (IP) address, or the like.

In some embodiments, mass memory 330 includes a RAM 332, a ROM 334, andother storage means. Mass memory 330 illustrates another example ofcomputer storage media for storage of information such as computerreadable instructions, data structures, program modules or other data.Mass memory 330 stores a basic input/output system (“BIOS”) 340 forcontrolling low-level operation of Client device 300. The mass memoryalso stores an operating system 341 for controlling the operation ofClient device 300.

In some embodiments, memory 330 further includes one or more datastores, which can be utilized by Client device 300 to store, among otherthings, applications 342 and/or other information or data. For example,data stores may be employed to store information that describes variouscapabilities of Client device 300. The information may then be providedto another device based on any of a variety of events, including beingsent as part of a header (e.g., index file of the HLS stream) during acommunication, sent upon request, or the like. At least a portion of thecapability information may also be stored on a disk drive or otherstorage medium (not shown) within Client device 300.

In some embodiments, applications 342 may include computer executableinstructions which, when executed by Client device 300, transmit,receive, and/or otherwise process audio, video, images, and enabletelecommunication with a server and/or another user of another clientdevice. In some embodiments, applications 342 may further include searchclient 345 that is configured to send, to receive, and/or to otherwiseprocess a search query and/or search result.

Having described the components of the general architecture employedwithin some embodiments, the components' general operation with respectto some embodiments will now be described below.

FIG. 4 is a block diagram illustrating the components of someembodiments. FIG. 4 includes dashboard engine 400, network 415 anddatabase 420. The dashboard engine 400 can be a special purpose machineor processor and could be hosted by a cloud server (e.g., cloud webservices server(s)), messaging server, application server, contentserver, social networking server, web server, search server, contentprovider, third party server, user's computing device, and the like, orany combination thereof.

According to some embodiments, dashboard engine 400 can be embodied as astand-alone application that executes on a server and/or user device(e.g., on a cloud server and/or on-prem on a user device or localstorage). In some embodiments, the dashboard engine 400 can function asan application installed on a device; and, in some embodiments, suchapplication can be a web-based application accessed by a device over anetwork.

The database 420 can be any type of database or memory, and can beassociated with a content server on a network (e.g., cloud server,content server, a search server or application server) or a user'sdevice (e.g., client devices discussed above in FIGS. 1-3 ). Database420 comprises a dataset of data and metadata associated with localand/or network information related to users, services, applications,content and the like. Such information can be stored and indexed in thedatabase 420 independently and/or as a linked or associated dataset. Asdiscussed above, it should be understood that the data (and metadata) inthe database 420 can be any type of information and type, whether knownor to be known, without departing from the scope of the presentdisclosure.

According to some embodiments, database 420 can store data and metadataassociated with users, operations, tasks, assets, files, projects,versions, synchronization events, schedules, images, videos, text,messages, products, items and services from an assortment of mediaand/or service providers and/or platforms, and the like.

According to some embodiments, database 420 can store data for users,e.g., user data. According to some embodiments, the stored user data caninclude, but is not limited to, information associated with a user'sprofile, user interests, user behavioral information, user attributes,user preferences or settings, user demographic information, userlocation information, user biographic information, and the like, or somecombination thereof.

In some embodiments, the user data can also include user deviceinformation, including, but not limited to, device identifyinginformation, device capability information, voice/data carrierinformation, applications installed or capable of being installed orexecuted on such device, and/or any, or some combination thereof. Itshould be understood that the data (and metadata) in the database 420can be any type of information related to a user, asset, location, job,operation, content, a device, an application, a service provider, acontent provider, whether known or to be known, without departing fromthe scope of the present disclosure.

As discussed above, with reference to FIGS. 1-2 , the network 415 can beany type of network such as, but not limited to, a wireless network, alocal area network (LAN), wide area network (WAN), the Internet, or acombination thereof. The network 415 facilitates connectivity of thedashboard engine 400, and the database of stored resources 420. Indeed,as illustrated in FIG. 4 , the dashboard engine 400 and database 420 canbe directly connected by any known or to be known method of connectingand/or enabling communication between such devices and resources.

The principal processor, server, or combination of devices thatcomprises hardware programmed in accordance with the special purposefunctions herein is referred to for convenience as dashboard engine 400,and includes layout module 402, storage module 404, modification module406, display module 408. It should be understood that the engine(s) andmodules discussed herein are non-exhaustive, as additional or fewerengines and/or modules (or sub-modules) may be applicable to theembodiments of the systems and methods discussed. The operations,configurations and functionalities of each module, and their role withinembodiments of the present disclosure will be discussed below.

Turning now to FIGS. 5-7 , embodiments are discussed that discloseexamples of how a dashboard can be displayed across separate platforms,on different types of devices and/or different types of operatingsystems or some combination thereof. It should be understood that theexample embodiments and depictions in FIGS. 5-7 are non-limiting, asvariations in the displayed user interface (UI) elements, as well as themanner in which a UI is transformed from one platform to another tomaintain the same look and feel would be understood by those of skill inthe art, and will be discussed in more detail below in relation toProcess 800 of FIG. 8 .

FIG. 5 illustrates a non-limiting example embodiment of a dashboardinstance being displayed in a web environment and a mobile environment.The web display 500 can be a displayed dashboard interface within abrowser executing on a user's personal computing device (e.g., alaptop), for example.

The mobile display 502 corresponds to the display of the dashboardinterface on a mobile device (e.g., a smart phone or tablet). In someembodiments, display 502 can correspond to a UI within a proprietaryapplication that provides the functionality for the dashboard. Forexample, as discussed above, display 502 can correspond to a mobile Apphosting and executing engine 400's functionality.

In some embodiments, display 502 can be a third party application or abrowser application interface that is executing on a mobile device.

As discussed in more detail below, the electronic or digital informationdisplayed on interfaces 500 and 502 are displayed in a manner thatleverages the capabilities of the displaying device in order to maintainthe look and feel of the dashboard and/or data being displayed.

By way of a non-limiting example, a user opens display 500 on hispersonal computer (e.g., laptop). After setting up the dashboard, thedisplay 500 is stored. The user then opens a mobile App on his mobiledevice and renders the dashboard as mobile display 502. As discussed inmore detail below in relation to FIG. 8 , display 502 is a modificationof display 500 based on the display and rendering capabilities, amongother features, of the mobile device providing display 502.

According to some embodiments, as discussed in more detail below, whenchanges are effected on display 500, they are automatically produced oroccur on display 502. This also occurs in the opposite direction fromdisplay 502 to display 500. This ensures that the dashboard iscontinuously displaying the same information on any instance that isrunning.

Thus, for example, two users viewing the dashboard at differentlocations on different devices are simultaneously viewing the same datawithin a dashboard configured to maintain the same viewing experiencebetween each user. This functionality also applies to the UIs of FIGS. 6and 7 , as discussed below.

FIG. 6 illustrates another non-limiting example embodiment of adashboard instance being displayed in a web environment and a mobileenvironment. FIG. 6 illustrates how tiles (or electronic cards)displayed within the dashboard are effectively displayed in a similarformat, layout and configuration to maintain the same look and feelacross varying display environments.

Similar to FIG. 5 , in FIG. 6 , display 600 is a web display within, forexample, a browser, and display 602 is a mobile display that correspondsto the display of the dashboard interface on a mobile device.

As discussed in more detail below, the electronic or digital informationdisplayed on interfaces 600 and 602 are displayed in a manner thatleverages the capabilities of the displaying device in order to maintainthe look and feel of the dashboard and/or data being displayed.

By way of a non-limiting example in accordance with some embodiments,the tiles within display 600 are displayed in a manner that enables allthree to be viewable within the display 602 of the mobile device. Forexample, since it would render the data unreadable to display the threecards of 600 in landscape on a horizontal axis as displayed in display600, within the mobile display 600, the dashboard is reconfigured todisplay the cards in a scrollable manner along a y-axis, thereby basingthe configuration of display 602 on the display features andcapabilities of the mobile device to ensure the look and feel ismaintained from display 600.

FIG. 7 illustrates yet another non-limiting example embodiment of adashboard, where an open tile displayed in a web environment (i.e.,display 700) is modified and reproduced for display within a mobileenvironment (i.e., display 702). In a similar manner as discussed abovein relation to FIGS. 5 and 6 , and discussed in more detail below inrelation to Process 800 of FIG. 8 , the display in display 700 is amodified version of display 702, and vice versa, which enables the samedata to be reproduced according to the display characteristics of thedisplaying device (and/or environment).

Turning now to FIG. 8 , Process 800 details a non-limiting embodimentaccording to some embodiments for automatically generating anddynamically updating a multi-displayed dashboard of consistent instanceson separate devices and/or network locations. According to someembodiments, the disclosed framework is configured to automaticallygenerate and dynamically update and display a dashboard of multipleprocesses and operations across platforms of different devices,operating environments and/or display capabilities, or some combinationthereof.

The development of various formats for content and different platformsfor providing a uniform experience with content has led to difficultiesin the display and access of the content. Content that is developed onone platform may not appear on another platform as intended by thecontent developer.

For example, a webpage designed for a laptop appears differently whenaccessed by a smart phone. As a result, the content developer may needto configure different various versions of a content item so that itmaintains a uniform look and feel on different platforms. This problemcan be exacerbated when multiple users are requesting and accessing thesame data from different locations, devices, locations and platforms.

For example, when a user accesses and shares content for an operation,they may use different formats for their text, image or video data, andsuch formats may be inherent or native to the device the user is using.

Thus, the disclosed systems and methods provide functionality forcomputerized tools to automatically configure content (e.g., a dashboardand the data displayed therein) so that it appears uniformly acrossdifferent platforms. According to some embodiments, the disclosedframework (via execution of engine 400), facilitates the generation of adashboard's configuration, layout and display, and then ensures thatsuch configuration, layout and display are maintained across differentcomputing/display environments with varying degrees of functionality fordisplaying and rendering the dashboard in a uniform manner. Thisultimately enables the content to be displayed on these platforms asintended by the generating user.

According to some embodiments, the dashboard discussed herein will bediscussed in reference to electronic or digital tiles or cards (referredto as tiles). However, it should not be construed as limiting, as anytype of digital information can be displayed within a dashboardinterface, whether known or to be known, without departing from thescope of the instant applications' functionality of maintaining the lookand feel of the dashboard across displays in a seamless manner. Forexample, the dashboard can display any type of image, text, video,multi-media, RSS data, graphics, graphs, icons, charts, augmentedreality (AR) depictions, virtual reality depictions (VR), messages,hyperlink (or URL) or any other type of interactive data or interfaceobjects that detail operations of an asset(s) at a location(s), and thelike, or some combination thereof.

According to some embodiments, as discussed herein, when a dashboardinterface (referred to as a dashboard, as illustrated in FIGS. 5-7 ) isopened and interacted with, the interactions are reproduced and providedto all other instances of the dashboard. In some embodiments, thechanges on one dashboard instance or version (e.g., operating on onedevice) can take effect on stored versions of the dashboard and/oropened versions operating on other devices. This reproductioneffectively provides a virtual deployment of what is occurring on onedashboard to occur on all other instances of the dashboard therebyenabling and facilitating a collaborative environment between users.

For example, as in FIG. 7 , when a tile is selected and opened to alarger view within a browser (700), the mobile version 702 is modifiedin a similar manner. The mobile modification and auto-display of theinteraction on another device occurs automatically and enables acollaborative environment to be realized so that users at differentlocations (or sub-locations within a single location) can effectivelywork together and view the same data. Additionally, this enables usersto leverage the enterprise capabilities of the disclosed dashboardframework, such that the work they perform on a browser can be readilytransferred and realized on their mobile device (and vice versa).

Therefore, for example, if a user works at his desktop, then has to goout the site, in some embodiments, the information is transferred to hisdevice in a intelligible and viewable manner in direct correspondence tothe browser instance, so that the user can view the data at the site.

One of skill in the art would understand that any modifications to thedata and/or layout performed on the mobile site can be reverse saved sothat the browser mirrors the actions on the mobile device in accordancewith some embodiments.

According to some embodiments of Process 800, Steps 802-804 areperformed by the layout module 402 of dashboard engine 400; Steps 806,812 and 816 are performed by storage module 404; Steps 808 and 818 areperformed by display module 408; and Steps 810 and 814 are performed bymodification module 408.

Process 800 begins with Step 802 where a set of tiles are identified.According to some embodiments, the tile can be in any format and/or ofany type, such as, but not limited to, a pareto card, a manufacturingexecution system (MES) card, an insight chart card, an alarms card, ageneric card and/or an alerts card. In some embodiments, the tiles canbe specific to a location, to a set of locations, to an asset at alocation, to set of assets, to an asset working multiple locations, to atime period, to a particular job, task or application/operation, and thelike, or some combination thereof.

In Step 804, dashboard information is received from a first displayenvironment, which provides an indication as to how the set of tileswill be configured, laid out and displayed within a dashboard displayexecuted within the first display environment.

For purposes of discussion only, the first display environment will beembodied as a laptop computer operating a browser to display adashboard. One of skill in the art would understand that the firstdisplay environment including a laptop computer is non-limiting, as anytype of display device and/or platform can be implemented as a firstdisplay environment.

According to some embodiments, this information can be received,determined or otherwise identified based on a type of criteria or set ofcriteria that dictates dashboard information. Such criteria can be basedon a user, a device, an operation, an asset, a platform, a network, atime, a location, and the like, or some combination thereof.

In some embodiments, a user can provide the dashboard information. Insome embodiments, the dashboard information can be automaticallydetermined based on and/or in accordance with user parameters, settingsor selections previously supplied by a user or suppled in connectionwith reception of the set of tiles. In some embodiments, the dashboardinformation can be based on the type of tiles. In some embodiments, thedashboard information can be automatically determined by the receivingdevice (e.g., the server) and/or based on the device used to initiallydisplay the dashboard.

In some embodiments, the dashboard information corresponds to a formator formatting and layout of the dashboard, and a manner in which thetiles will be displayed and capable of being interacted with therein.The dashboard information can correspond to, but is not limited to, adisplay size, color, dimension, font, layout, format, configuration,layer, organization, pixel data, resolution, scrollability, amount ofavailable screen real estate on a device's display, operating system ofa device, network bandwidth, service provider of the device and/orserver, user identity, and the like, or some combination thereof.

In some embodiments, in Step 806, the dashboard information is stored ina database (e.g., data store 420). In some embodiments, the storage ofthe dashboard information and information related to the set of tilescan involve the creation of data structures corresponding to a dashboardinstance or version. Thus, new data can be created that is capable ofbeing interacted with, manipulated/modified and updated, therebyincreasing the efficiency in which metrics about an operation can beretrieved and provided to a requesting entity or user.

In some embodiments, the dashboard information can be stored as atemplate. The template can be configured according to the dashboardinformation such that its configuration, sizing and capabilities fordisplaying data are in accordance with the received information of Step804. In some embodiments, the template can comprise modules fordisplaying tiles and the functionality afforded the interactive tiles,such, as but not limited to, expanding, contracting, scrolling,augmenting, searching, highlighting, providing supplemental information,and/or any other type of interactive behavior tiles provide users as away of detailing data of operations.

Thus, in some embodiments, by way of a non-limiting example, at thispoint in Process 800, a dashboard is configured and capable of beingdisplayed on a device of a first display environment.

For example, in some embodiments, as a result of the execution of Steps802-806, a dashboard is configured and displayed—see examples in FIGS.5, 6 and 7 , displays 500, 600 and 700, respectively.

Continuing with Process 800, in some embodiments, in Step 808, a requestto access a dashboard and display it from a second display environmentis received. The second display environment can be a smart phoneexecuting a mobile application installed therein. One of skill in theart would understand this embodiment of a second display environment asnon-limiting, as any type of device and any type of application can beutilized without departing from the scope of the instant disclosure.

In some embodiments, in Step 810, in response to receiving the request,display and rendering capabilities of the second display environment aredetermined, derived, retrieved, extracted or otherwise identified. Insome embodiments, the request in Step 808 can comprise display andrendering capability information of the second display environment. Insome embodiments, Step 810 can include a process for retrieving and/orextracting the configuration of the second display environment from dataavailable to engine 400 on the network.

The display and rendering capability information of the second displayenvironment can include, but is not limited to, a display size, color,dimension, font, layout, format, configuration, layer, organization,pixel data, resolution, scrollability, amount of available screen realestate on a device's display, operating system of a device, networkbandwidth, service provider of the device and/or server, user identity,and the like, or some combination thereof.

In some embodiments, Step 810's analysis of the second displayenvironment's data to identify its display capabilities can be performedby any type of known or to be known computational analysis technique,including but not limited to, vector analysis, data mining, computervision, machine learning, neural network, artificial intelligence, andthe like, or some combination thereof.

In some embodiments, in Step 812, the data for the dashboard stored inStep 806 is retrieved. In some embodiments, such retrieval can be basedon a search query that includes information requesting the dashboardinstance (e.g. an operation or job identifier) and identifyinginformation related to the second display environment. In someembodiments, the query can further include the confirmation informationof the second display environment.

In some embodiments, in Step 814, the retrieved dashboard information isanalyzed based on the display and rendering capability information ofthe second display environment (from Step 810). According to someembodiments, such analysis can involve any type of known or to be knowncomputational analysis technique, including but not limited to, vectoranalysis, data mining, computer vision, machine learning, neuralnetwork, artificial intelligence, and the like, or some combinationthereof.

As a result of the analysis of the stored dashboard information, thedashboard information (e.g., the template for displaying the tileswithin the dashboard UI) can be modified to conform to the display andrendering capability information of the second display environment. Insome embodiments, this enables the dashboard to be displayed within thesecond display environment at its highest quality while maintaining thelook and feel it had from the first display environment.

In some embodiments, the modifications performed in Step 814 caninvolve, but are not limited to, modifying the traits, characteristicsand/or attributes of the dashboard information. In some embodiments, thetemplate data and/or modules' data and/or configurations can be modifiedand stored in a similar manner.

In some embodiments, the modifications can be added to the storeddashboard information, such that only the changes to the traits aresaved to storage (e.g., the stored dashboard data objects havesupplemental information stored and associated therewith withinstorage). This enables efficient storage (e.g., reduction on memoryusage) while ensuring an efficient retrieval of data specific to thesecond display environment (in response to the request of Step 808 andsubsequent requests).

According to some embodiments, the modifications performed in Step 814result in a compiled new version of the dashboard. Thus, additional dataobjects or data structures can be created for the second displayenvironment and stored in association with the dashboard informationwithin storage. Step 816. Such storage can be effectuated as a secondversion of the dashboard information specific to a second displayenvironment or specific to a type of the second display environment(e.g., a smart phone or type of platform or OS, for example).

In some embodiments, the storage of Step 816 (and Step 806) can involveand/or utilize any type of database or storage configuration ortechnology, including but not limited to, blockchain or a look-up table(LUT), for example. In some embodiments, the storage occurring in Steps806 and/or 816 are cloud-based.

In some embodiments, the analysis of Step 814 may determine that thedisplay and rendering capability information matches the dashboardinformation; therefore, no modification is required and Process 800ends. For example, first display environment and second displayenvironment have computing devices, associated displays and/or networkcharacteristics that are at least similar to a threshold degree wherebythe dashboard template stored in Step 806 is the best option forreproducing the dashboard within the second display environment with thesame look and feel as the first display environment.

In Step 818, the modified dashboard display is automaticallycommunicated and caused to be displayed within the second displayenvironment.

Thus, for example, as a result of Steps 808-818, the dashboard'sdisplayed in FIGS. 5, 6 and 7 as displays 500, 600 and 700,respectively, are reconfigured and automatically displayed as displays502, 602 and 702, respectively.

In some embodiments, the modification in Step 814 can be performed onthe network such that the dashboard is updated and then is sent to thesecond display environment. This, for example, increases efficiency inthe way tiles and other dashboard data is displayed as the processing ofthe dashboard's display modification(s) occurs on the server side as apre-processing step thereby offloading the resources required to performthe manipulation and modification of the dashboard/tiles from thedisplay device.

In some embodiments, as tile data is updated (e.g., received tile dataas in Step 802), the tile data can be stored (e.g., Step 806) andpre-processed in a similar manner as discussed in relation to Steps814-816. Then, the dashboard can be dynamically updated based on theupdated tile data, which can change which tiles are displayed, how theyare organized and/or configured and the like, as discussed above.

In some embodiments, based on network capabilities, the dashboardinformation and modification instructions can be sent to the seconddisplay environment for modification on the client side.

For the purposes of this disclosure a module is a software, hardware, orfirmware (or combinations thereof) system, process or functionality, orcomponent thereof, that performs or facilitates the processes, features,and/or functions described herein (with or without human interaction oraugmentation). A module can include sub-modules. Software components ofa module may be stored on a computer readable medium for execution by aprocessor. Modules may be integral to one or more servers, or be loadedand executed by one or more servers. One or more modules may be groupedinto an engine or an application.

For the purposes of this disclosure the term “user”, “subscriber”“consumer” or “customer” should be understood to refer to a user of anapplication or applications as described herein and/or a consumer ofdata supplied by a data provider. By way of example, and not limitation,the term “user” or “subscriber” can refer to a person who receives dataprovided by the data or service provider over the Internet in a browsersession, or can refer to an automated software application whichreceives the data and stores or processes the data.

Those skilled in the art will recognize that the methods and systems ofthe present disclosure may be implemented in many manners and as suchare not to be limited by the foregoing exemplary embodiments andexamples. In other words, functional elements being performed by singleor multiple components, in various combinations of hardware and softwareor firmware, and individual functions, may be distributed among softwareapplications at either the client level or server level or both. In thisregard, any number of the features of the different embodimentsdescribed herein may be combined into single or multiple embodiments,and alternative embodiments having fewer than, or more than, all of thefeatures described herein are possible.

Functionality may also be, in whole or in part, distributed amongmultiple components, in manners now known or to become known. Thus,myriad software/hardware/firmware combinations are possible in achievingthe functions, features, interfaces and preferences described herein.Moreover, the scope of the present disclosure covers conventionallyknown manners for carrying out the described features and functions andinterfaces, as well as those variations and modifications that may bemade to the hardware or software or firmware components described hereinas would be understood by those skilled in the art now and hereafter.

Furthermore, the embodiments of methods presented and described asflowcharts in this disclosure are provided by way of example in order toprovide a more complete understanding of the technology. The disclosedmethods are not limited to the operations and logical flow presentedherein. Alternative embodiments are contemplated in which the order ofthe various operations is altered and in which sub-operations describedas being part of a larger operation are performed independently.

While various embodiments have been described for purposes of thisdisclosure, such embodiments should not be deemed to limit the teachingof this disclosure to those embodiments. Various changes andmodifications may be made to the elements and operations described aboveto obtain a result that remains within the scope of the systems andprocesses described in this disclosure.

What is claimed is:
 1. A computing device comprising: one or moreprocessors; and a non-transitory computer-readable memory having storedtherein computer-executable instructions, that when executed by the oneor more processors, cause the one or more processors to perform actionscomprising: receiving, over a network, electronic data corresponding toan operation of a set of physical assets at a location, the electronicdata compiled as tiles, such that each tile corresponds to an operationof an asset within said set of physical assets; receiving dashboardinformation setting a configuration of a dashboard for a first device,the received dashboard information comprising information indicating howthe tiles are to be displayed on a user interface (UI) of the firstdevice; storing, in a database associated with the computing device, thereceived dashboard information; receiving, over a network, from a seconddevice, a request to access and display the dashboard; analyzing, basedon said request, capability information of the second device, and basedon said analysis, determining display and rendering capabilities of thesecond device; modifying, in response to the second device request, thestored received dashboard information based on the determined displayand rendering capabilities of the second device to obtain modifieddashboard information, the modified dashboard information comprises dataselected from a group consisting of: display size, color, dimension,font, layout, format, configuration, layer, organization, pixel data,resolution, scrollability, amount of available screen real estate,operating system, network bandwidth, service provider and user identity;compiling a version of the dashboard for display on a display of thesecond device based on the modified dashboard information to obtain acompiled dashboard; and automatically causing, over the network, thecompiled dashboard to be displayed on the display of the second device.2. The computing device of claim 1, wherein said stored dashboardinformation further comprises the electronic data of the set of tiles.3. The computing device of claim 1, wherein said database is acloud-based storage.
 4. The computing device of claim 1, wherein saidrequest to access and display the dashboard comprises said capabilityinformation.
 5. The computing device of claim 1, wherein the dashboardinformation is stored as a template indicating a configuration, formatand layout of the set of tiles.
 6. The computing device of claim 1,wherein the capability information of the second device comprises dataselected from a group consisting of: display size, color, dimension,font, layout, format, configuration, layer, organization, pixel data,resolution, scrollability, amount of available screen real estate,operating system, network bandwidth, service provider and user identity.7. The computing device of claim 1, wherein the actions furthercomprise: receiving information related to an update of electronic datarelated to a first tile within the set of tiles; and updating, within adashboard displayed on the first device, content displayed within thefirst tile based on the received information.
 8. The computing device ofclaim 6, wherein the actions further comprise: retrieving, from thedatabase, second device dashboard information for the second device;modifying a first tile based on the second device dashboard information;and communicating information related to the modified first tile to thedashboard for display on the second device.
 9. The computing device ofclaim 8, wherein said compiling a version further comprises: creating anew version of the dashboard based on the determined display andrendering capabilities of the second device; and storing said newversion in association with the dashboard information.
 10. The computingdevice of claim 9, wherein said communicating information is based onsaid new version.
 11. The computing device of claim 8, wherein saidcompiling a version further comprises: modifying attributes of thestored received dashboard information based on the determined displayand rendering capabilities of the second device; and storing themodified attributes in said database in relation to the stored receiveddashboard information.
 12. The computing device of claim 11, whereinsaid communicating information is based on the dashboard information andstored modified attributes.
 13. The computing device of claim 1, whereinthe actions further comprise: causing, over a network, a dashboarddisplay on the first device and the dashboard display on the seconddevice to operate as a collaborate environment, such that modificationson the first device are automatically caused to be performed on thesecond device, and modifications on the second device are automaticallycaused to be performed on the first device.
 14. A computing devicecomprising: one or more processors; and a non-transitorycomputer-readable memory having stored therein computer-executableinstructions, that when executed by the one or more processors, causethe one or more processors to perform actions comprising: receiving,over a network, electronic data corresponding to an operation of a setof physical assets at a location, the electronic data compiled as tiles,such that each tile corresponds to an operation of an asset within saidset of physical assets; receiving dashboard information setting aconfiguration of a dashboard for a first device, the received dashboardinformation comprising information indicating how the tiles are to bedisplayed on a user interface (UI) of the first device; storing, in adatabase associated with the computing device, the received dashboardinformation; receiving, over a network, from a second device, a requestto access and display the dashboard; analyzing, based on said request,capability information of the second device, and based on said analysis,determining display and rendering capabilities of the second device;modifying, in response to the second device request, the stored receiveddashboard information based on the determined display and renderingcapabilities of the second device to obtain modified dashboardinformation, the modified dashboard information comprises data selectedfrom a group consisting of: display size, color, dimension, font,layout, format, configuration, layer, organization, pixel data,resolution, scrollability, amount of available screen real estate,operating system, network bandwidth, service provider and user identity;compiling a version of the dashboard for display on a display of thesecond device based on the modified dashboard information to obtain acompiled dashboard; and automatically causing, over the network, thecompiled dashboard to be displayed on the display of the second device.15. The computing device of claim 14, wherein the actions furthercomprise: retrieving, from the database, second device dashboardinformation for the second device; modifying a first tile based on thesecond device dashboard information; and communicating informationrelated to the modified first tile to the dashboard for display on thesecond device.
 16. The computing device of claim 15, wherein saidcompiling a version further comprises: creating a new version of thedashboard based on the determined display and rendering capabilities ofthe second device; and storing said new version in association with thedashboard information.
 17. The computing device of claim 16, whereinsaid communicating information is based on said new version.
 18. Thecomputing device of claim 15, wherein said compiling a version furthercomprises: modifying attributes of the stored received dashboardinformation based on the determined display and rendering capabilitiesof the second device; and storing the modified attributes in saiddatabase in relation to the stored received dashboard information. 19.The computing device of claim 18, wherein said communicating informationis based on the dashboard information and stored modified attributes.